Onboarding doc project for TPM | Blurgs Innovations Private Limited

Onboarding Overview

Hello there <Insert name of the new hire>!

This is going to be your one stop solution for the upcoming few days, till you get your feet wet. The idea is that through this document you will hit the road running.

We will go over a brief introduction to the company - this will not include what we normally tell to the outsiders on our socials. This is what we want the team to understand this company is meant.

So lets jump right in!

Introduction to company

Users

Our users are operators in organizations. Big organizations. Private or Government or Quasi? Everything.

These operators are mid to senior level professionals who have spent considerable amount of time in the maritime domain and expect the design language to be mature (read jargon heavy).

Market

Our market is the broader maritime domain. This includes everything from shipping ports, to surveillance agencies, to coast guards and navies, to international watch-dog organizations.

It is a vast and diverse landscape but do not worry we will give you a soft immersion to all of them in the coming months.

Product

It is a application. Think of windows applications. Made with .Net. We have tabs upon tabs of information in the platform, each meant to convey specific use case - piracy, search and rescue, travel time estimate etc.

Further we have categorized the information in an event based table which can be filtered based on a number of criteria, some available in the table some not.

Team

The team is mainly divided into two broad functions - technical and business. The technical team is further divided into - Software Development, UI/UX and Machine Learning. The business team is further divided into - operations and growth/marketing.

Introduction to function

Who are we?

We are bunch of young guns. Quite literally. The average experience of the team is roughly 2 years. What we lack in the numbers we compensate in enthusiasm. Sounds cliche right? believe it holds true in this org. The split between tech and business is roughly 70/30. Though we encourage our team members to know all the functions to the point that the evening tea breaks are fun but not more.

What is the teams function?

The team you will be part of does not exist! Sounds scary, i know. Your team is the executive staff and the technical staff. The teams function here is to gather user feedback, do user calls and then translate it into features for the platform. The life of a feature has various stake-holders at different ages. It passes from the hands of the executives to the design team to the software and machine learning team.

Why does the team exist?

As i said, the team does not exist. Yet. The team which is going to be incepted will have one primary focus and that is all - How do we make the platform as beneficial to the user as possible. The goal is not to improve one aspect of the platform, be it design or functionality or usability but create a balance so as to we are able to drive each of these aspects of the product.

Impact of the team

The impact of the team is quite clear - No User Feedback -> No Useable Platform.

First 7 days

The first seven days are going to be the most formative in getting to understand the user. We trust your technical capabilities otherwise you would not have been reading this document in the first place. So lets get you to understand what you will need the most and what you might be lacking the most.

We have 5 ICPs.

We are going to arrange a 1-1 call with a user from each ICP, do not worry you will not be stranded and left alone to your own devices in the meeting, you will be accompanied one executive who has worked with the user in the past and has good rapport.

After this we would like you to go to the drawing board and give us from the conversation these _ things:

How many hours do they spend on the platform? Is it too much, Is too less?
What is an ideal amount of time for this user to spend on the platform?
What is the one feature that this user interacts with the most?
Is the user looking for delight? Can this delight be created?
Identify any and all Pareto effects that might be at play while interacting with the platform.

Team Conversations

The conversations we have in this org are in two modes - formal ones which we document scrupulously and informal ones which if they get documented even by mistake we would have to burn those papers.

You will have a soft intro for formal meetings with each team lead along with their team, and this will be facilitated and guided by the team lead .

For getting you to understand the work arounds about the day-to-day, be it the food situation at the workplace to the best parking spots. We will be assigning you a buddy. You can reach out to them anytime and if you do not, they will.

30-60-90 day plan

Time Period	Core Outcomes	Why?
First 30 days	Understand the platform both as someone who uses it and someone who is going to build it Talk to almost all the organizations we have as clients	So that you can get into the shoes of the user
30 - 60 days	Start designing one new feature Take this feature from inception to completion	You will get to understand the development process, end to end.
60 - 90 days	Implement automated ways to get user interaction data Implement a feedback mechanism that has the potential to be automated	This will set you up to concentrate more creative and full-filling parts of the job.